-
Notifications
You must be signed in to change notification settings - Fork 684
Compile with clang-7.0 #2754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile with clang-7.0 #2754
Conversation
Well, I messed this one up, too. |
@wille-io You don't have to close a PR just because a fix didn't work out. (Unless you give up on the fix completely.) You can just keep working on the same branch and push / force push it to GitHub. It will update the PR automatically. It is a better approach than opening a new PR for every try. Please see the GitHub Flow intro (section "Discuss and review your code"). |
@akosthekiss Can we please have a talk about me failing git @ irc? Sadly nobody was answering there for several days. |
jerry_debugger_scope_variable_type_t was not explicitly sized by the compiler as 8bit, accept uint8_t instead (you still can call the fn with a jerry_debugger_scope_variable_type_t) JerryScript-DCO-1.0-Signed-off-by: wille-io [email protected]
reopen |
3fea62c
to
1a80416
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (informal)
Next try.
jerry_debugger_scope_variable_type_t
was not explicitly sized by the compiler as 8bit.Instead the fn could accept a
uint8_t
. You still can call the fn with a jerry_debugger_scope_variable_type_t as parameter.